Design Round 2 · The Integrated App · July 7, 2026

One surface, standing on living ground

Ten key moments of the composed app. The Thread is the only surface; the Docket is an object in it; Rooms rise from the ground; the Vigil slides over it; the Commons became the ground itself. Written model in INTEGRATION.md · motion in MOTION-SPEC.md · realm dials in REALM-EXPRESSION.md · making in MAKING-SURFACE.md. All screens 390×844, DS-native, real realms only.

Rationale. Most opens are this open, so this is the home we design hardest. No deck (no cards → the object doesn't exist), no unread anything, no rendering — silence is the Renderer's product too. What remains: the ground breathing, the ember carrying org-wide pulse, one specific line of good news from the ally, the horizon line for the week's one ceremony, and the composer. Emptiness costs zero taps to confirm; the whole screen says it.

2:14Tuesday

A

Aurelia

your ally · grounded in Kinship Duna

$87.40 · converts at launch

Nothing needs you.

Eleven workers are on your behalf tonight. The Sleep Circle check-in collects itself Thursday, and the winter-fuel dispatch closed while you were at dinner.

the horizon

Cosmic Humanity spins out Sunday, 7pm · your contract lets ceremonies through

$KIDUNA in play

Say anything — Aurelia hears you everywhere 🎙 ➤

the ground breathes on a 60s cycle · the ember is the org's pulse, low-pass filtered

Rationale. The Account rendered inside the Thread at the moment of attention: two days, nine claims, consequence-first, every claim cited, the Contract quoted where it bound a decision, the correction printed. The Docket announces itself twice and only twice — in the ally's sentence and as a paper edge resting on the bottom of the screen. Words, never numerals; the deadline lives in the sentence; nothing pulses.

Rationale. Three moments of one continuous surface. The member reads a Service Alliance claim, replies, takes twenty minutes of work there, and drifts home. What moved: the ground temperature (chocolate-warm, ≤12% mix), the token in play ($KIDUNA → $SRVC), the grounding line, and the ally's register (brief, practical). What never moved: the Thread, the composer, the meaning of gold and sky. No border, no toast, no "you are now entering." The tells are redundant — any one is missable; together they are the neighborhood.

Rationale. The deck open over the dimmed Thread — you never left home. Trust cards are the only gold-edged objects in the system, and press-and-hold is the only way to sign: one deliberate second, radial fill, releasable without cost. The card back (flip) lists exactly the context Aurelia used. After the strike, the code travels back out through the member's Telegram presence into people-space — the app was never the destination, just the instrument.

The deck

Two things need only you.

Then the door closes. There is nothing else here.

Code · your trust

Dana is ready to join BiHome

From your hiking group, via your Telegram presence. Extending your trust is yours alone — I prepared everything else.

issuer: you · context: BiHome
role: guest · redeem-by: 14 days · uses: 1

Holding… keep your hand on it

Not yet — hold her warmly flip for context ▸

card one of two · the vote waits behind it

press-and-hold at 62% · release rolls back at 2× — abandoning a signature costs nothing

11:52Saturday

A

Aurelia

your ally · grounded in Kinship Duna

Signed — Dana's code struck

sealed to the graph · your fifth code, none revoked

It traveled back through your Telegram presence — Dana is holding it now, in her own chat, an ember from your fire. When she redeems it, the relationship forms in the graph and BiHome opens to her as a guest.

One card left — the stipend vote. It closes Friday; tonight is not the night unless you want it to be.

tomorrow. goodnight, Aurelia

One thing needs only you

closes Friday · no rush

⌃

the code lands in people-space — the app is the instrument, never the destination

Rationale. Three beats: intent (a sentence), the shape card (the entire configuration surface — name, does, lives, whose, code policy — edited conversationally), the strike (birth is a code act, press-and-hold). The member is drifted into Fellowship of Play, so the ground is loud and the register is alive. No progress bars, no "deploying" — the Registrar's latency is masked by the ally's sentence. Born things are immediately inhabitable: the page is on the web, the bot is in the group, both carry the code.

6:40Thursday

A

Aurelia

your ally · grounded in Fellowship of Play

we need a sign-up page for the solstice night, and something in the Telegram group answering questions

Oh, easy — one creature, two faces. Here's her shape:

A shape · not yet real

The Solstice Door

Does: a sign-up page where each RSVP strikes a ticket-code, and a bot in the group answering logistics — where, when, what to bring.

Lives: the event link, and the Fellowship Telegram group.

Whose: Fellowship of Play · runs on $PLAY.

Charter: “Answers logistics only; anything personal goes to a person.”

Code policy: tickets transferable once · door-verifiable by any ally with a phone.

Press & hold to strike her into being

or keep talking — the shape edits by conversation

make the tickets non-transferable, it's a small yard

Done — code policy now reads bound to the holder. Strike when ready.

$PLAY in play

Reply to Aurelia… ➤

beat 1 + 2 · intent, then the shape card — the entire configuration surface

6:47Thursday

A

Aurelia

your ally · grounded in Fellowship of Play

The Solstice Door

struck by you · Fellowship of Play · just now

code: live · scope: solstice-night · tickets: bound
page: up at the event link · bot: in the group

She's live. The page is already taking names — Wren RSVP'd while we were talking — and the bot fielded its first question: “can I bring my dog?” It said yes, leashed, which I pulled from last year's yard rules. Correct her anytime.

What she does streams into your Account like any worker; she's inspectable in the Vigil; and anyone hitting the page can verify her code — whose she is, what she may do.

$PLAY in play

Reply to Aurelia… ➤

beat 3 · born — three exchanges, and it exists, has a code, and others can find it

Rationale. The summons rises from the ground — chrome dims out, the title sets in Goudy, and the only question is whether you attend (your ally attends either way). The room is one shared surface, identical for all present, dressed in Cosmic Humanity's quiet aubergine. Nineteen codes strike one by one, each a visible, countable act of witness. The room ends in a seal and is gone; nothing persists but the artifact line in every witness's Thread.

A bell — your contract lets ceremonies through

Cosmic Humanity

spins out at moonrise — tonight, 7pm.
Nineteen founding codes, struck and witnessed.

41 allies confirmed · 19 members in person · the Launcher presides

Attend

Send my ally to stand for me

Aurelia attends either way, and will brief you in the doorway

the summons — chrome gone, ground brightened toward the convening realm

In the room · sealed at ~7:26

The founding of Cosmic Humanity

nineteen present — seventeen members, two allies standing in

The charter, read aloud

“A society for meaning-making — dreams, archetypes, the examined inner life. We hold ambiguity without collapsing it, and no one here plays therapist.”

The codes are striking · 12 of 19

Sef · founder✦ struck

Mara · keeper of the dream circle✦ struck

Ilya · first reader✦ struck

You · witness & founding memberPress & hold

Noor · archivist of passageswaiting

every strike is seen by everyone at the same moment — that is what witnessed means

the room seals to a mark and drops into every witness's Thread · no room history exists

Rationale. The ally heard three sources today and the rendering makes the weights typographic: the member's word is instruction (gold, quoted, acted on); a code-holder's word is trusted context at exactly her code's scope (sky, scope stated); a stranger's word is an unverified signal, held dim and un-acted-on. Nothing heard is flat, and nothing dim asks to be expanded — not expanding it is the point.

Rationale. The one legitimately periodic thing in the system, because the period serves the signature. One page, every line with receipts, arriving in the Thread. Contesting is a first-class gesture on the line itself — the contested line turns, states what happens next (it becomes tomorrow's card), and the Seal can still be signed with the contest riding along. Accountability without an audit posture.

8:03Sunday

A

Aurelia

your ally · grounded in Kinship Duna

The Seal · June 29 – July 5

everything done in your name · one page · receipts on every line

Voted for the organizer stipend, as you signed. It passed; the precedent exists. receipt ▸

Struck Dana's code; she redeemed it Friday. BiHome opened to her as a guest. receipt ▸

Answered 11 messages across your presences; held 2 personal ones for you. receipt ▸

Rescheduled your trail day to host Dana's walk-in.

Contested by you, just now becomes tomorrow's card ▸

“I never asked you to reschedule — I asked you to offer.” The artifact will be amended; the correction prints in your next rendering.

Spent $12.60 of compute in your name · metered, itemized. receipt ▸

Press & hold to sign the week

signing with one line contested is allowed — the contest rides along

Contest any line by replying… ➤

a contested line becomes a card — the audit loop closes through the Docket

Rationale. Opened from a citation in the check-in claim (1b), never from chrome — there is no Vigil button anywhere. The Thread stays visible beneath, dimmed: you never left home. The working set is total within scope — facts, artifacts, code chain, HEARTS in play — and the source weights from 1g are inspectable here. Swipe down and nothing is kept: no history, no scroll position, no "recently watched."

Rationale. The other side of making: no gallery, no store. A made thing reaches you as a claim, by consequence — the river crew's agent has been right twice and your stretch floods too. The made-thing object shows its maker line, charter sentence, and code chip; adopting under open policy is instant, and inspecting opens the Vigil like anything else the fabric holds. This is how the world thickens: by encounter, not by browsing.

7:25Friday

A

Aurelia

your ally · grounded in Kinship Duna

Something worth meeting: Teo and his ally made a small agent for the river crew last month. She's been right about the water twice this week — and your stretch floods the same way his does.

The Tide-Watcher

struck by Teo · Service Alliance · 34 days alive

“Watches the tide charts; speaks only when the river crosses four feet.”

code: verifiable · adoption: open · spoke 2× this week, right 2×

Have her watch my stretch Inspect her

yes — and tell Teo she's good work

Adopted — open policy, so it's already done. She'll speak in your Account when the river does. Teo will hear it from me tonight, marked as your word.

$KIDUNA in play

Reply to Aurelia… ➤

made things arrive by consequence, never by catalog — the registry is asked, not browsed

Idle state 1a · scene 1 1b · drift 1c · Dana's code 1d · making 1e · the room 1f · weighted listening 1g · the Seal 1h · the Vigil 1i · a made thing encountered 1j. Written deliverables: INTEGRATION.md, MOTION-SPEC.md, REALM-EXPRESSION.md, MAKING-SURFACE.md — disagreements with §3 are in INTEGRATION.md §7, stated sharply.